Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(search_family): Fix indexes loading in the FT.SEARCH and Ft.AGGREGATE commands #3955

Conversation

BagritsevichStepan
Copy link
Contributor

fixes #3782, #3659

@BagritsevichStepan BagritsevichStepan self-assigned this Oct 21, 2024
src/server/search/search_family.cc Outdated Show resolved Hide resolved
src/server/search/search_family.cc Outdated Show resolved Hide resolved
src/server/search/search_family.cc Outdated Show resolved Hide resolved
src/server/search/doc_accessors.h Outdated Show resolved Hide resolved
@@ -80,7 +80,7 @@ search::SortableValue ExtractSortableValueFromJson(const search::Schema& schema,
} // namespace

SearchDocData BaseAccessor::Serialize(const search::Schema& schema,
const FieldsList& fields) const {
const SearchFieldsSvList& fields) const {
SearchDocData out{};
for (const auto& [fident, fname] : fields) {
out[fname] = ExtractSortableValue(schema, fident, absl::StrJoin(GetStrings(fident), ","));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure why this turned into "sortable". What is sortable about it? 🙂

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It returns sortable value?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, but it's not exclusively used for sorting - that's the confusing part. Its used for all document access. It just returns a document value in one of the value types

@BagritsevichStepan BagritsevichStepan force-pushed the df.search/fix-aggregate-load-option-indexes branch from 1bd7078 to 15b633c Compare October 27, 2024 12:12
…GATE commands

fixes dragonflydb#3782, dragonflydb#3659

Signed-off-by: Stsiapan Bahrytsevich <stefan@dragonflydb.io>
@BagritsevichStepan BagritsevichStepan force-pushed the df.search/fix-aggregate-load-option-indexes branch from 15b633c to e61afa2 Compare October 27, 2024 12:13
@BagritsevichStepan BagritsevichStepan merged commit 5dcad85 into dragonflydb:main Oct 27, 2024
9 checks passed
@BagritsevichStepan BagritsevichStepan deleted the df.search/fix-aggregate-load-option-indexes branch October 27, 2024 20:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

LOAD option does not behave as expected in the FT.SEARCH and FT.AGGREGATE commands
3 participants